Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1102

reference: 755-tree-1
name: 1102
tree-preservation-order: undefined
755-tpo-1
uprn
address-text
point: POINT (-1.011053 50.888346)
geometry: MULTIPOLYGON (((-1.010996 50.888340,-1.010999 50.888351,-1.011007 50.888361,-1.011019 50.888369,-1.011035 50.888375,-1.011052 50.888376,-1.011070 50.888375,-1.011086 50.888370,-1.011099 50.888362,-1.011107 50.888352,-1.011110 50.888341,-1.011107 50.888330,-1.011100 50.888320,-1.011087 50.888312,-1.011071 50.888306,-1.011054 50.888304,-1.011036 50.888306,-1.011020 50.888311,-1.011008 50.888319,-1.010999 50.888329,-1.010996 50.888340)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL